Hotspot Not working on LTE or 3G.. and even via USB cable tethering. Connect but no internet access. Found out the hard way today and had to resort to Starbucks
Hotspot Not working on LTE or 3G.. and even via USB cable tethering. Connect but no internet access. Found out the hard way today and had to resort to Starbucks
Hotspot Not working on LTE or 3G.. and even via USB cable tethering. Connect but no internet access. Found out the hard way today and had to resort to Starbucks
I tried to change my mobile network mode to GSM/WCDMA auto, guess what? WiFi tethering worked again (even with WPA2 security enable).
Go try again!
PS I am on Rogers Wireless
I just tried that setting again, and still no go for me. I'm on Rogers as well. I'm actually running Quantum 1.25 on my SGS3, but it uses that CM base code. I'll check some more in that forum.
Just updated - and looks like I'm working now with GSM/WCDMA mode!! Thanks for the suggestion!
Awesome! Good job! Let's hope the fix for WiFi hotspot under LTE (Canadian carriers) will be coming soon.
[Q] SIM Unlock?
I'm moving from AT&T to T-Mobile and taking my D2ATT with me. I got the unlock code from ATT, but it's not working to unlock the phone. What method works these days?
I'm currently on the 9/8 nightly.
I'm moving from AT&T to T-Mobile and taking my D2ATT with me. I got the unlock code from ATT, but it's not working to unlock the phone. What method works these days?
I'm currently on the 9/8 nightly.
Alright I give up. What happened to the long press volume option for skipping to next song? Am I blind?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hi all,
For those of who on Rogers Wireless and having problem on WiFi tethering under LTE network on their CM 10.2, here is the solution I found on CM forum. Credit goes to op of http://forum.cyanogenmod.com/topic/76413-wifi-tethering-and-cm-102-issues/.
I tested it on my Rogers rooted SGS3 with the latest NIGHTLY "10/04" and working well to share WiFi under LTE network to my TouchPad!!!
Cheers!
For those of who on Rogers Wireless and having problem on WiFi tethering under LTE network on their CM 10.2, here is the solution I found on CM forum. Credit goes to op of http://forum.cyanogenmod.com/topic/76413-wifi-tethering-and-cm-102-issues/.
I tested it on my Rogers rooted SGS3 with the latest NIGHTLY "10/04" and working well to share WiFi under LTE network to my TouchPad!!!
Cheers!
I encountered the exact same issue trying to unlock my d2att (with a friends t-mo SIM card) while running CM10.2 nightly's. I had unlocked a couple of different phones before this way, also rooted running custom ROMs, without issue. However, after trying to get the code to take on a number of occasions and trouble shooting with ATT tech support I found no other solution and ended up flashing back to stock, reset the flash counter and sure enough it took the unlock code right away ....
Sorry I don't have any better news for you
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Yup flashing back to stock TW is the only way to get the unlock code to work. I ended up staying on a deoxed TW Rom after I unlocked.... access to multi window was my motivation which I don't even use... funny how that works.
Clarification- doesn't have to be stock just a TW ROM.
Clarification- doesn't have to be stock just a TW ROM.
Last edited:
Phone rebooted into safe mode and widgets are gone is there a way to restore in titanium backup?
At first My Play Store App disappeared. So I factory reset thinking that'll solve the problem. Now I cant even sign into my account. In setup>>>Accounts>>> Theres no option for Google Account... Can any one help me with this?
I couldn't find a general Q&A for cm10.2. Would this be a good place to get some help or advice?
CM 10.2 lock screen fullcrash possible fix
i know other users on 10.0 10.1 10.2 and 11 are experiencing reboots and crashes and would like to add my take on what worked for me.
sorry for posting here but im a new poster. i have been fallowing the forums since october 2013
i was experiencing random crashes on 10.2 and previously pacrom milestone based on CM 10.*
all crashes happend just as i had put the phone into my jacket pocket.
i could replicate the issue by repeatedly locking the screen
i have had only two crashes(found my phone off in pocket) in the last month after changing my lock screen delay, crashes down from 5-12 times weekly
-settings - lock screen - powerbutton instantly locks [] disable/unchecked.
- automatic lock - set to more than immediate. ( ex. 15 seconds)
please post your findings and hit thx if this has helped you. ty
i know other users on 10.0 10.1 10.2 and 11 are experiencing reboots and crashes and would like to add my take on what worked for me.
sorry for posting here but im a new poster. i have been fallowing the forums since october 2013
i was experiencing random crashes on 10.2 and previously pacrom milestone based on CM 10.*
all crashes happend just as i had put the phone into my jacket pocket.
i could replicate the issue by repeatedly locking the screen
i have had only two crashes(found my phone off in pocket) in the last month after changing my lock screen delay, crashes down from 5-12 times weekly
-settings - lock screen - powerbutton instantly locks [] disable/unchecked.
- automatic lock - set to more than immediate. ( ex. 15 seconds)
please post your findings and hit thx if this has helped you. ty
I've been having an interesting problem for a while in CM 10.2, and now still in CM11 (M3 release)..
Occasionally, I notice that the CPU seems to get 'stuck' at 384 Mhz. It took me a while to figure this out, the symptom is that the entire phone/interface gets sluggish, and if I am streaming audio over bluetooth, I get audio dropouts. I eventually figured out that what happens is the CPU is sitting at 384 Mhz, despite being at 99% or 100% cpu usage. This is most common when I am using the phone for navigation, and sometimes streaming bluetooth audio at the same time using PowerAMP.
I tried resolving it by using a tasker rule to change the minimum CPU speed when I put it in my car dock... but that doesn't seem to have helped, if I go into performance options when it is lagging, I see the current CPU speed as 384 Mhz, even if the minimum CPU speed is showing as higher than that.
I am running CM11-20140210-SNAPSHOT-M3-d2att, with UCUEMJB bootloaders.
Has anyone else seen this type of behavior? Am I outdated on bootloaders?
Occasionally, I notice that the CPU seems to get 'stuck' at 384 Mhz. It took me a while to figure this out, the symptom is that the entire phone/interface gets sluggish, and if I am streaming audio over bluetooth, I get audio dropouts. I eventually figured out that what happens is the CPU is sitting at 384 Mhz, despite being at 99% or 100% cpu usage. This is most common when I am using the phone for navigation, and sometimes streaming bluetooth audio at the same time using PowerAMP.
I tried resolving it by using a tasker rule to change the minimum CPU speed when I put it in my car dock... but that doesn't seem to have helped, if I go into performance options when it is lagging, I see the current CPU speed as 384 Mhz, even if the minimum CPU speed is showing as higher than that.
I am running CM11-20140210-SNAPSHOT-M3-d2att, with UCUEMJB bootloaders.
Has anyone else seen this type of behavior? Am I outdated on bootloaders?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
9An amateur FAQ
I have consolidated some information regarding frequent issues with the most recent nightly releases. Hopefully someone finds this useful, since I've dealt with most of them myself and I see someone ask about these things daily. If any of the info here is wrong or misleading please don't hesitate to correct me (just kidding, I know you won't)
GPS
- When the option was added to use an external GPS it broke the default source to be undefined. Go to "System Settings->Location Services->GPS Source" and make sure "Use Internal GPS" is selected.
- Some other update changed something with the permissions of the location services settings. Go to "System Settings->Location Services" and uncheck and recheck all the options to force it to ask for the proper permissions again.
4G LTE/Wireless Data
- Make sure you are aware of the difference between the service providers' terminology and the "real"/CM terminology (AT&T 4G is actually HSPA+, AT&T 4G LTE is actually 4G).
- Go to "System Settings->More->Mobile networks" and make sure LTE is selected under Network Mode.
- Go to "System Settings->More->Mobile networks->Access Point Names" and verify versus known good LTE APN settings. Currently Rogers LTE APN is missing or incorrect. You will have to enter it manually or wait for the proper defaults to be merged.
- You may have lost your IMEI. Check "System Settings->About Phone->Status". If your IMEI shows 0 you may have to follow the instructions in the IMEI recovery thread. After restoring your IMEI you may still need to do additional steps to restore LTE. To avoid this headache back up your IMEI before you lose it using the above thread. Make sure you try just rebooting first to see if that fixes the missing IMEI.
- ** Seems to be fixed on 09/12 **
Currently you need to reboot after installing for the first time or upgrading to a new nightly in order to get any data signal.
Wi-Fi
- Some people report problems with Wi-Fi signal or connection. Try going to "System Settings->Wi-Fi->Menu/Advanced" and un-check "Avoid Poor Connections".
Volume/Sound Problems
- Audio drivers are currently a work-in-progress. Updates are still coming all the time.
- If you have no sound try turning the volume all the way down then up again for alarms, calls, notification, etc.
- Try re-selecting your ring tones in the app or clearing cache and/or data for that app.
- Call volume is known to be a bit loud now. Try pulling the phone away from your face during the call so that the screen turns on and turn up/down the volume.
- There seems to be an issue with Google Now voice recognition mic volume. Try talking into the noise cancellation mic (top).
- If your phone is not speaking Google Now results or street names in Navigation properly make sure you are using English (US) in the language settings (other languages/nationalities are currently not supported).
Camera/Gallery
- There is currently no option to store to external SD (yet).
- The built in gallery does not sync to Picasa. This is a known bug.
- **Reverted and reportedly fixed in 9/10**
Swipe to gallery feature was "broken" by the addition of pinch to zoom. To get it to work swipe outside of image and buttons (in the grey area).
Battery Life
- Battery calibration is wiped after first installing or upgrading. Wait a full cycle before trusting percent reported.
- Install BBS to track alarms and wake locks.
- Battery use after clearing caches after upgrading is high. Wait til it is finished rebuilding before gauging drain.
- Other kernels give more control over battery and performance. You can try those but don't report any other bugs here if you do.
Screen Flicker
- Has improved recently but can be seen occasionally, particularly with 3rd party keyboards or graphics intensive apps.
- Going to "System Settings->Developer Options" and choosing "Disable HW Overlays" fixes the flicker at the expense of performance.
USB Storage
- There is no UMS (Generic USB Mass Storage) mode by default on our phones. You may need to install MTP drivers or a different OS that supports it. There are apps that allow UMS access but there are drawbacks.
- If you followed any of the procedures in the IMEI thread and did not properly revert to MTP mode you may need to do so before being able to access your storage via USB.
Home button wake
- Going to System "Settings->Performance->Processor" and increasing the minimum CPU frequency from 384 to 486 is reported to fix it.
64GB+ SD Cards
- CM will not directly support the exFAT format due to licensing restrictions
- You can format as FAT32 (with the restriction of not being able to have files over 4GB each)
- Not sure if it is supported at the moment, but in the future you should be able to format as ext (fixes the 4GB file problem, but makes the card unreadable by Windows without special tools)
Anything gapps related involving non-recommended gapps
- For example problems with text messaging when using inverted gapps
- Use recommended gapps.
Anything system related involving non-CM kernels
- Use the default kernel.
Installing/Upgrading
When updating from Nightlies MAKE SURE you are downloading the CM10 zip file. The CM9 weekly files show up in the same list.
The M flagged zip files are the same as every other nightly, except care is taken in the days/week before releasing the M edition to not introduce any new features into Nightlies that might break the system. This means that if you flash only the M files you are less likely to run into "show-stopping" bugs. After the M edition is released developers will continue adding new features to the Nightlies that may or may not result in instability.
The recommended nightly upgrade procedure should be:
- Backup/Nandroid
- Format "/system" (under Mounts and Storage)
- Wipe cache
- Wipe Dalvik cache (under Advanced)
- Install Nightly ROM zip
- Install gapps zip
- Reboot System
You may be able to get away with only:
- Backup/Nandroid (not technically required, but you're a crazy-pants if you don't)
- Wipe cache
- Wipe Dalvik cache (under Advanced)
- Install Nightly Rom zip
- Reboot System
Apps Force Closing/Other Strange Behaviour That Other People Are Not Reporting
- Try running Fix Permissions from recovery
- After backing up, try a Factory Reset combined with the above flashing steps to see if the error occurs on a clean system (Factory Reset does not wipe/format your SD card(s), only erases all apps and app/system data)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app3Great bit of info put together by unit_vector
I have consolidated some information regarding frequent issues with the most recent nightly releases. Hopefully someone finds this useful, since I've dealt with most of them myself and I see someone ask about these things daily. If any of the info here is wrong or misleading please don't hesitate to correct me (just kidding, I know you won't)
GPS
-When the option was added to use an external GPS it broke the default source to be undefined. Go to "System Settings-> Location Services-> GPS Source" and make sure "Use Internal GPS" is selected.
-Some other update changed something with the permissions of the location services settings. Uncheck and recheck all the options on the above screen to force it to ask for the proper permissions again.
4G LTE/Wireless Data
-Currently you need to reboot after installing for the first time or upgrading to a new nightly in order to get any data signal.
-Make sure you are aware of the difference between the service providers' terminology and the "real"/CM terminology (AT&T 4G is actually HSPA+, AT&T 4G LTE is actually 4G).
-Go to "System Settings->More->Mobile networks" and make sure LTE is selected under Network Mode.
-Go to "System Settings->More->Mobile networks->Access Point Names" and verify versus known good LTE APN settings.
-You may have lost your IMEI. "Check System Settings->About Phone->Status". If your IMEI shows 0 you may have to follow the instructions in the IMEI recovery thread http://xdaforums.com/show....php?t=1801997. After restoring your IMEI you may still need to do additional steps to restore LTE. To avoid this headache back up your IMEI before you lose it using the above thread. Make sure you try just rebooting first to see if that fixes the missing IMEI.
Wi-Fi
-Some people report problems with Wi-Fi signal or connection. Try going to "System Settings->Wi-Fi->Menu/Advanced" and un-check "Avoid Poor Connections".
Volume/Sound Problems
-Audio drivers are currently a work-in-progress. Updates are still coming all the time.
-If you have no sound try turning the volume all the way down then up again for alarms, calls, notification, etc.
-Try re-selecting your ring tones in the app or clearing cache and/or data for that app.
-Call volume is known to be a bit loud now.
-There seems to be an issue with Google Now voice recognition mic volume. Try talking in to the noise cancellation mic (top).
-If your phone is not speaking Google Now results or street names in Navigation properly make sure you are using English (US) in the language settings (other languages/nationalities are currently not supported).
Camera/Gallery
-Swipe to gallery feature was "broken" by the addition of pinch to zoom. To get it to work swipe outside of image and buttons (in the grey area). **Reverted and reportedly fixed in 9/10**
-There is currently no option to store to external SD (yet).
-The built in gallery does not sync to Picasa. This is a known bug.
Battery Life
-Battery calibration is wiped after first installing or upgrading. Wait a full cycle before trusting percent reported.
-Install BBS http://xdaforums.com/show....php?t=1179809 to track alarms and wake locks.
-Battery use after clearing caches after upgrading is high. Wait til it is finished rebuilding before gauging drain.
-Other kernels give more control over battery and performance. You can try those but don't report any other bugs here if you do.
Screen Flicker
-Has improved recently but can be seen occasionally, particularly with 3rd party keyboards or graphics intensive apps.
-Going to "System Settings->Developer Options" and choosing "Disable HW Overlays" fixes the flicker at the expense of performance.
USB Storage
-There is no UMS (Generic USB Mass Storage) mode by default on our phones. You may need to install MTP drivers or a different OS that supports it. There are apps http://xdaforums.com/show....php?t=1711009 that allow UMS access but there are drawbacks.
-If you followed any of the procedures in the IMEI thread and did not properly revert to MTP mode you may need to do so before being able to access your storage via USB.
Home button wake
-Going to System "Settings->Performance->Processor" and increasing the minimum CPU frequency from 384 to 486 is reported to fix it.
64GB+ SD Cards
-CM will not directly support the exFAT format due to licensing restrictions
-You can format as FAT32 (with the restriction of not being able to have files over 4GB each)
-Not sure if it is supported at the moment, but in the future you should be able to format as ext (fixes the 4GB file problem, but makes the card unreadable by Windows without special tools)
Anything gapps related involving non-recommended gapps
-For example problems with text messaging when using inverted gapps
-Use recommended gapps.
Anything system related involving non-CM kernels
-Use the default kernel.
Installing/Upgrading
When updating from Nightlies MAKE SURE you are downloading the CM10 zip file. The CM9 weekly files show up in the same list.
The M flagged zip files are the same as every other nightly, except care is taken in the days/week before releasing the M edition to not introduce any new features into Nightlies that might break the system. This means that if you flash only the M files you are less likely to run into "show-stopping" bugs. After the M edition is released developers will continue adding new features to the Nightlies that may or may not result in instability.
The recommended nightly upgrade procedure should be:
-Backup/Nandroid
-Format /system (under Mounts and Storage)
-Wipe cache
-Wipe Dalvik cache (under Advanced)
-Install Nightly ROM zip
-Install gapps zip
-Reboot System
You may be able to get away with only:
-Backup/Nandroid (not technically required, but you're a crazy-pants if you don't)
-Wipe cache (It looks like dalvik-cache is included in the /cache partition on our phones - it isn't for all phones - so a /cache wipe should cover Dalvik as well. I'm no expert though, so don't take my word for it if you have problems NOT wiping Dalvik cache specifically)
-Install Nightly Rom zip
-Reboot System
Apps Force Closing/Other Strange Behaviour That Other People Are Not Reporting
-Try running Fix Permissions from recovery
-After backing up, try a Factory Reset combined with the above flashing steps to see if the error occurs on a clean system (Factory Reset does not wipe/format your SD card(s), only erases all apps and app/system data
Anything system related involving non-CM kernels
-Use the default kernel.2Hi all,
For those of who on Rogers Wireless and having problem on WiFi tethering under LTE network on their CM 10.2, here is the solution I found on CM forum. Credit goes to op of http://forum.cyanogenmod.com/topic/76413-wifi-tethering-and-cm-102-issues/.
I tested it on my Rogers rooted SGS3 with the latest NIGHTLY "10/04" and working well to share WiFi under LTE network to my TouchPad!!!
Cheers!2[SIZE=+2]This thread is designed ONLY for the support of thedevices.[/SIZE]
This thread is designed to help keep the dev thread clean and clear for the dev's to do their magic. So please feel free to ask any questions about the ROM, but trolling and flaming will not give great results and will be reported.
The main Dev thread is located HERE
GAAPS can be found HERE
ClockworkMod can be found HERE listed as "Samsung Galaxy S3 (AT&T)"
THE NIGHTLY's Can be found HERE
Post your findings/fixes with your install procedure, along with your CWM version, your kernel and any mods
Thank you kangi26 for having created this informational thread
Fixes and Mods:
First Circle Battery Mod by Tiffany84!
http://xdaforums.com/showpost.php?p=29092238&postcount=1070
Crysis Battery Icon CM10 Build 7/29 by tiffany84:
http://xdaforums.com/showpost.php?p=29761975&postcount=23
http://d-h.st/2oH
JT Inverted Productions JusTunBean Inverted JB
http://xdaforums.com/showthread.php?p=29343474
Bypass Exchange Security settings:
http://xdaforums.com/showthread.php?t=1117452
Thanks r0ckvn for the link
LogCat thanks to sublimejosh2000:
Open your terminal on your phone and type:
su
logcat > /sdcard/log.txt
It will continue to write to the file as long as terminal is open and when you experience the bug, it will catch it. When you reboot you should have a nice text file for uploading to the thread
*** If you are getting errors playing Media Files or are seeing multiples of the same image or Grey items. This is "Ghosting", for some reason(what/why this is is unknown to me). The Fix:
Go to Settings/Apps/All/scroll down to Media Storage, and Clear Data. Reboot, and Scan your media again. Depending how much you have will determine how long it takes. This will happen again when rebooting, maybe not the first or second reboot, but it'll happen again
[SIZE=+3]I am having trouble installing/running/updating CM10[/SIZE]
