yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] big_doubleT:
Has anyone been losing their IMEI by flashing the latest nightlies? I want to flash this rom but a little paranoid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twostep665:
I'm on the 9/19 build. Anyone noticing any issues with the screen not timing out and turning off on its own? I just noticed it and must have just started doing it. Gonna try a reboot and see if that helps. Will most likely flash newest build tonight.

Can't say enough how much I love this ROM.

EDIT: Reboot seems to have resolved it for now but yall keep an eye out for it on your phones to see if the issue pops up. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bcn17:
Update nightly - 5 minutes - works everytime.

SOURCE: http://xdaforums.com/showthread.php?t=1766443

Download latest nightly from get.cm

1. Reboot Recovery

2. Backup

3. Wipe data /factory reset

4. wipe cache

5. wipe dalvik cache

6. install zip from SD card

7. restore --> advanced --> data only

8. reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slackercow:
this is the 'dirty install' method. you should be wiping between updates, otherwise we get the same people coming back and giving 'bug reports' without having done a clean install. it's not that much extra work.

method i have seen around that will give you less problems:

backup current CM10 install

WIPE *factory+cache+dalvik

install new CM10/gapps

advanced restore -> data from from last backup

EDIT: bcn17 beat me to it: http://xdaforums.com/showpost.php?p=31887251&postcount=4760
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
But if you think you've found a bug, you shouldn't post here until doing a full wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] k2snowboards88:
You really don't have to wipe though. It almost always works fine without wiping. I've never had a problem. I do backup, however, so that in the event that it doesn't work I can wipe. I don't see any need to wipe preemptively though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Regarding battery life, for anyone who isn't seeing a huge improvement I recommend a wipe.

I usually would not be at 100% for more than a couple minutes after unplugging (or even less), but after flashing my own 0922 kang, and doing a full wipe, I've been at 100% for an hour and 15 mins. Pretty stellar improvement if you ask me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] derberts:
Which kernel are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dano9258:
No don't use the check for updates. Just go to download rom and select the newest one that you want. It will list them out... I only wipe the dalvik cache.

---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------

False! I have the free version and do it all the time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
This happened to me too actually, but I thought that was too good to be true, so I restarted and then I was at 87%. Almost as though the battery indicator froze. This happened to me on a previous build too (9/18 maybe) but that time it was saying the phone was charging when it wasn't. Restart, and it was down to 90%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajonesma:
I get that even without a full wipe. Just dirty flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I've been dirty flashing from day one previews over in cyanogen's thread. Haven't had a problem aside from the occasional SOD.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kd5dmg:
Clear data and cache on maps app. That fixed it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] heaiser:
Anyone else still having call volume problems? Still crazy loud for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Yes. Try changing the volume up and down and see of that helps. Some report its a temp fix. Works for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Is this just the battery fuel guage fixing itself?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radeon_x:
That's only part of the problem. The real problem is that the lowest possible volume is way too high. Way higher than stock. All AOSP/AOKP ROMs still have this problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] techphets:
I'm curious what everyone likes about this ROM. The one feature I was looking forward to with jelly bean, offline dictation, did not seem to work yet and I'm wondering what everyone likes about about cm10 compared to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] energyracing:
Does anyone know the reason behind the change in Superuser? In the Superuser app, it now shows Superuser v3.1.4 and su binary 3.2 (they used to both be 3.2), if I try to update the binary, nothing happens when I tap it. Also, some apps now require me to "Allow" Superuser access 5x in a row before it works. Anyone know what's up?

EDIT: Nevermind. Read through posts first, ask questions later lol. My bad.

http://xdaforums.com/showpost.php?p=31850563&postcount=4729
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
[Wonky Navigation]

You really only need to clear all the Google map app data. Mine was repeating old text over and over clearing solves it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ferris2375:
That seemed to help, as far as I can tell. So far anyway. :)

And yeah to the guy who said it may be hardware problems (home button not waking). No, it's not hardware. This is the only ROM that gives me trouble with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Quick question guys,

Is there a way/theme to make the messaging font dark/black? I bought the bluematted theme, the keyboard is darker but can't seem to find a way to get that dark background.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rayoubi:
I have a werid bug. When I press the app drawer button then go back to my home pages. I have to press menu twice, getting annoying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
I assume so. If you used less than 1% battery life in an hour and 15 minutes, then the whole battery would last over 125 hours. As awesome as that would be, I just don't think we're quite there yet. It seems like it just gets stuck for some reason, and a reboot would fix it. I wonder if just restarting the statusbar, through Rom Toolbox or something, would do the trick too? If it happens to me again, I'll give it a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Inverted MMS apk can be found in the themes section. I believe that's what you're looking for, a black background to the messaging app?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] derberts:
I find cm10 much snappier and fluid in every category.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mentalmuso:
I can't seem to get my blazing 50mbps dwn and 20mbps up LTE speeds on the PTA APN. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
The number is different by location. You'd have to get it for your area. If you put in a different one, it just asks you to press a bunch of options, and then doesn't go through because it says you don't have a mailbox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psychoboogie:
can you share wallpaper? saw it on mycolorscreen but the box account was overloaded.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kevinl86:
Yeah I just put my own number 1(area code)number in the VM number setting/call my VM/Hang up/Wait a few secs/ATT Visual Voicemail picks it up and wants me to set back up real quick. Tada. Doneski
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ghstudent:
Hold an empty spot on the home screen and select the cyanogen mod wallpapers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
volm down + power
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhoopes517:
Out of curiosity, Is calling working for everyone?

I flashed this build last night to no avail, was kinda disappointed because I thought it was daily driver material xD

But, minus that, everything else brought my spirits back up! CM10 is running nice! Keep up the great work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
So is

this

working on this port of JB?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mentalmuso:
I don't have any issues with calling or the daily "phone" functionality of this build. Camera is a bit quirky, but it works. Try the full wipe and reinstall. If you haven't already
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fruitycups:
so how does one restore completely to stock for warranty purposes? Just via odin or is there a custom kernal running?

Also, its alright if we choose to forgo rom manager right? never a fan so i always left it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhoopes517:
Odin.

Tool-Kit also allows you too. But if you go to the Android Development forum and grab the stock rom you can then extract and flash it through Odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fruitycups:
hm sounds good. so you don't need to restore a kernel or anything? its as simple as going in, extracting, loading it into the pda slot and clicking start. Nothing else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfleischman:
My question is why are all the ROMS for this phone saying the files have to be placed on the internal SD. What is wrong with the external one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhoopes517:
It reflashes stock Kernel, I am sure.

I rooted my S3 last night. Flashed this CM10. It didnt work. Grabbed stock rom. Flashed that through Odin. And had a full stock phone last night.

Till now, Just installed CWM and am now installing CM10 again. xD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fruitycups:
Ah got it.

Wanted to be sure because i know some roms flash custom kernels. When i asked last time, I think someone told me that you had to flash the stock kernel first before flashing the actually stock firmware.

didnt want to end up with a expensive paper weight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhoopes517:
Same here. Just flash it through Odin. You will be fine. If you dont trust doing it yourself, just plug it in and go through the toolkit and download stock rom and flash through odin. Option 8, in the toolkit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iastonish:
What cm9 features have been implemented so far? Guessing it's still to early to see cm10 themes/theme chooser working right?

Thanks for all the hard work Cynogen Mod team!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I had to go back to stock. In 42 mins off the charger I was to 82%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
The linked commit includes:

- Power menu Reboot

- Power menu screenshot

- Profiles

- Lock screen Calendar

- Lock screen Weather

- Notification light customization

- Battery light customization

- IME Selector notification toggle

- and a few more things to support Settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greg25:
Theres a fix for the camera issue already posted somewhere in this thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Help me understand ...

Please help me understand exactly what you did. I, too, am having issues with Superuser. Although I found a fix by installing an older version of Superuser, I'd like a better alternative. Also, and I know this is an irrelevant matter, I prefer the black background in SuperSU.

So, you said you installed SuperSU, and then used the "Switch" function in SuperSU. However, the "Switch" entry in SuperSU says the following:

Switch superuser app

Cleanup to switch to another superuser app

I interpret this to mean that if you want to switch to ANOTHER superuser app, OTHER than SuperSU. That's not what I want to do. I want to switch FROM Superuser TO SuperSU.

Therefore, can you explain exactly what you did so that I can do the same?

Thanks,

Peter

Addendum: I figured it out. Thanks!

Addendum 2: Perhaps I'm biased, but SuperSU seems to be more fluid, and it seems to register far quicker when I use an app that needs root access. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erezak:
Peter - it shouldn't be necessary after the next nightly. See this commit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
wouldnt it be possible to grab the su binary, and supersu apk then inject them into the the CM10 CWM zip and flash it in recovery, just a thought might be a bit more complicated but it should work =)

edit: looks like its already been fixed judging from the last post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
We'll see ...

I was quite sure they would get the Superuser issue fixed, and now it appears to be the case.

I'm downloading the latest NIGHTLY now, and we'll see. Regardless, and I know it's simply a personal preference, but I much prefer the UI in SuperSU. Anything that uses a black background "should" be more battery friendly, right? Correct me if I'm wrong.

Either way, thank you for letting me know.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
New weather button for Samsung Cameras

Latest build (9/23) added a weather button to the camera? Does anyone know what this is about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
You can flash SuperSu in recovery mode. It will replace Superuser. I did without any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Superuser works well now. :)

You know, I prefer having an uncomplicated flash, and now that Superuser is working well, and knowing that I only go into the app on very rare occasions, I'll stick with it.

Thanks!

Peter

Addendum: I have noticed one strange behaviour: When I open Mobile ODIN, I have to press the Superuser prompt 9 times to finally get it to open completely. With SuperSU, I only had to press the "allow" once, wait a few seconds, and that was it. Hmm.

Addendum 2: Okay, that's it ... I'm sticking with SuperSU. No problems with it, but still issues with Superuser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dgfriedl:
I'm on CM10 M1 and offline dictation works. I know it's running when I start to get crazy translations. :)

Be sure that you are using the default jelly bean keyboard and put the phone in airplane mode to test.

-darren
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Exostenza:
My brother is running CM10 on his phone and recently "media" has been chewing his battery up in a matter of hours and his phone is constantly burning up. Which program does this relate to so we can either clear the app data or just get rid of it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
I also noticed afterwards that LTE was off. It really does make a big difference on battery life heh.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lostboy702:
Finally got s/u to work properly, now it's butter, smooth, fast and has great battery life.

I'll post an update after running a few more tests....

Great job guys....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
I'm not getting any sound in youtube or on my bell mobile tv,is this a bug?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AmazingSpanoMan:
I am still having Bluetooth disconnects in the middle of a call as well as garble call audio especially after using a music app like Pandora that requires a reboot to restore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Does 09/23 still have super user issues updating? Dony want to flash if the issue is still there....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajonesma:
It does, but I've only had the problem using ktweaker to set the settings for the KT747 kernel by ktoonsez
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
I think I will wait until its resolved fully since it screws up when i use bloatfreezer to disable stuff it asks like 6x also doesnt update binaries hopefully it will be resolved soon
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GHOSTIVVI:
I just installed supersu and don't have that issue anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] techphets:
I was hoping exchange services would use less battery with cm10 compared to stock. Not the case so far. I
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maturola:
The price of push email is battery life, if you want the exchange services to drain less of your battery, set your account to check every 30min. or every hour.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
How did you get superuser uninstalled and have SuperSU take over?

EDIT: Never mind. I used this trick in this thread: http://xdaforums.com/showthread.php?t=1767435
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dennis0201:
I wonder how to search contacts? It seems like CM10 doesn't work well by this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Yeah, I'll try to look into that, any link?

PoWeReD By that SeXy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] heaiser:
What do you mean? There is a search button in the people app. You can also search in the Google search bar I believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VirtualNobody:
Anyone else having WiFi issues? Starting with builds about a week ago, my WiFi has been flakey. I'm connected but my icons are grey, not blue. I need to reboot the phone to get it to reconnect.

I had the same problem with my Cappy and SIII on the stock ROM. Worked great on CM7 on the Cappy and CM9 on the SIII. WiFi seems flakey on CM10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drybones5:
Here are some things I'm been dealing with for a week now.

Super User can't remember allowed apps for access. Sometimes it'll also crash.

Goo manager seems to crash quite often while performing tasks, though it could be the constant SU permissions and crashing.

Some times, not often, the device will have no G apps services and requires a reboot to fix the issue.

Not sure this is worth noting, but the GS III's home button takes some pressure to press to wake up the device from idle/sleep but works perfectly fine when it is awake.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Grey instead of blue simply means that the Google Sync isn't connected, the connection is still available.

Sent from my SAMSUNG-SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anudist:
Install SuperSU, fixes that SU problem, been discussed in this thread already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] heaiser:
Home button issue is a known issue. I've started getting used to using the power button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
I'm still having wifi issues on the 9.23 build. It connects and works for about 2 minutes and then the internet just drops. Wifi is connected, but the icon is stuck in the up arrow position and I have ever to toggle the wifi off/on to get another 2 minutes. Screen is never off. Link speed drops to 1mbps so this is definitely a power save issue. Cm10 has no wifi power save options, just when to shut wifi off. Also my router runs tomato and t

Wpa2 psk. My nexus 7 has no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatsupnow:
Has anybody had alot of screen flicker on the latest build?

Galaxy SIII via XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
Yup, a lot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatsupnow:
Is there some kind of fix or no?

Galaxy SIII via XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Disable HW overlays in developer options for a temp fix and see if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
9/23 Rom

New Apex launcher is not working. Looks like Apex update pushed overnight. I've been using Apex all along, until now.

(Update) Apex is broken not related to cm10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Exact same thing happens to me on stock and all aosp ROMs. Only using the UCALH leak fixes it. I haven't tried the newest at&t ota though. It seems something with my FiOS modem/router doesn't agree with the phones WiFi. My nexus 7 and skyrocket and also my girlfriends galaxy nexus work fine on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jammol:
Home buttom has been an issue since beginning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Even though the changelog doesn't mention anything, 9/24 seems to have fixed the SU bug. Not getting pestered about SU access time and time again.

FYI, I never went the SuperSU route. Wanted to see if this got fixed "natively".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Wow i didnt know if the issue was still there so i fladhed and installed super su right away.I was still on 09/19.No wifi issues here but yea dont know what happened with the su issue i didnt wanna keep waiting either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VirtualNobody:
When it happens, there is no internet connectivity at all...Email doesn't sync, web browsers don't work, etc...It's not just Google Sync.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Great fix for Superuser issue until ...

I'm glad you got your Superuser issue resolved.

I have what appears to be a great fix, that is, until we know with certainty that the Superuser issue in CM10 is resolved.

Once you perform these steps, you really don't need to do anything in the future, even after flashing new NIGHTLY's.

1) Download and install SuperSU

2) Open SuperSU and go into settings

3) Click on "Switch superuser app" and then select "Continue"

This will effectively remove both Superuser and SuperSU from your app drawer ... BUT DON'T WORRY!

4) Reboot into Recovery

5) Perform a Nandroid backup

6) Reboot

7) Go back into Google Play and re-install SuperSU

You should now have SuperSU as your root manager, and it works very smoothly ... plus the UI is better-looking, in my opinion.

Let's say you now want to flash a new NIGHTLY ...

Perform the steps in this thread: http://xdaforums.com/showpost.php?p=28616039&postcount=1

After you're done, you'll actually have two superuser apps, both SuperSU and Superuser.

Now, after you finish flashing the latest NIGHTLY, flashing the latest GAPPS, and performing the Advanced DATA Restore, and after you're back at your home screen, simply open your SuperSU app. This time, however, Superuser will ask for root permission. Once you say yes, then Superuser will no longer be used. SuperSU will take over with all other apps.

This effectively puts Superuser to the side on all future root permission requests, and allows SuperSU to take over, and we know it works very well.

Once the entire Superuser situation is 100% resolved, uninstall SuperSU BEFORE performing the above steps, especially before you do your Nandroid. This way, when you do the advanced data restore, you will not automatically re-install SuperSU.

It's working perfectly for me.

I hope this was clear enough.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
What is the UCLAH fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
UCLAH is a modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
How do we get that on this CM10 nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit_vector:
Superuser not remembering granted apps

For anyone who is still having a problem with Superuser repeatedly asking for permissions on 9/23 or 9/24 make sure you at least wipe /system under Mounts and Storage, and clear the Superuser app data once you start up for good measure. I did so and my Superuser works without pestering me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mitchdickson:
This is a development thread. Head to Q&A.

Sent from my Motorola DynaTAC 8000X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
9/24 SuperUser annoyance fixed

Just wanted to confirm that the persistent SuperUser allow-dialog problem is gone in 9/24, and that no extra voodoo steps are necessary to fix it, since I just upgraded from 9/23 and only cleaned cache+dalvik as usual.

(Tested with AdAway, and TiBu: Permission remembered from old appdata instead of asking permission a dozen times)