yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Strange, I have the opposite issue. I have about 3 gigs of music on the internal sdcard, and only 3 albums show up in Apollo. I'm going to try moving it to external tonight to see if it changes anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
I am seeing screen flashes when typing using SwiftKey as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyruskane:
SMS fails to send longer but well under 160 character messages

Anyone else using the cm-10-20120808-3-UNOFFICIAL-d2att version having issues sending semi-long txts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jimmiray007:
SD Errors

"Originally Posted by sublimejosh2000

Has anyone else have problems getting media from the external SDcard to scan. I tried a re-scan by deleting data in Media Strage. After I did that on the 7/29 build, I have not been able to get these back. I did not see this reported yet."

Sorry if this is a little off topic

Not sure if this helps but my Xoom Tablet and Galaxy Nexus running stock jelly bean have the same issue. Only files added using Android Transfer will appear (especially with stock gallery app) Files could be found using ES File Explorer. When I pull the SD card and do file transfers on the LapTop, return card to Phone or Tablet...the files are not available to Android Transfer or Stock gallery. I would think that its something in Jelly Bean that would require the MTP transfer to generate some sort of pointers or log files for the system. Thats all I got, sorry if this was not a good place to post this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Correct. This is the nature of MTP as I see it. For proof of concept, anyone who wants to find out the hard way, clear app data on Android media storage, and then when the gallery is empty try connecting to the PC and see if you have any media. The folders don't even show up for me at all. After the media storage is rebuilt (which mine isn't even doing right now) it will show them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
And that's where I'm getting confused; I dual-mount my external SD card as USB Mass Storage and dump files into my media folders (this disables the MTP daemon) and Apollo sees all my music just fine. If I switch back to MTP mode without even running a rescan, I see all the files just as I did in UMS mode.

Side note; I'm using Windows 8 on every PC I connect to, even my work machine, so maybe Windows 8 did something to MTP to make it work better?

___________________________________

This discussion has gotten quite a bit off topic at this point; I think we can all agree that MTP and the media scanner seem to work properly in the current build of CM10, as only 1 person has stated that their media scanner doesn't work, and that was seemingly caused by clearing the media storage data.

I'd be glad to continue this discussion elsewhere, but on the topic of CM10, you should probably just nandroid, full wipe, and reinstall CM10. If everything works fine at that point, you know that it's not an issue with CM10. (Although clearing the data shouldn't break the scanner.) You can always just restore your nandroid after the test to go back to how things were.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
How are you dual mounting as Mass storage? I am also on W8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
http://xdaforums.com/showthread.php?t=1807873

After swapping modes, just go to the charm bar, settings, control panel, "Devices and Printers" and rightclick-remove the phone, then replug the USB cord. It'll detect as a USB mass storage. Repeat process to swap back to MTP. (It's pretty picky, but it works.)

Also, please see my last post, as I added to it after you replied.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
This is an issue with the way AOSP/AOKP handle texts > 160 characters. On stock Samsung firmware, up to 500 characters send as an SMS without splitting, on CM10, the default app will split them at 160 characters. Go SMS will fail unless you enable splitting. Mighty Text, which supports messages up 500 characters, will fail to send since once it's sent to the phone from the web app, the phone attempts to convert it to an MMS.

I would love to know if this is something that can actually be remedied. No rush, but just curious. Ability/toggle to send up to 500 characters without splitting or converting to MMS would be fantastic.

EDIT: I see your texts are < 160 characters. In which case I have no idea. The only issue I've had with regards to that is rapidly sending texts, they fail instead of pending if one is the process of sending.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Back on topic: I'm also getting random reboots. It was running stable for about 2 hours, and after receiving a phone call the screen turned 28 shades of green and the phone rebooted. Since then, I've seen it reboot twice more in the past 10 minutes, and once had it lock up on the lockscreen not accepting input. I'll try to grab logcats ASAP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
same here, random reboots with the screen color changing.

as a matter of fact, I got 3 reboots within a minute now.

least stable build for me so far :( might have to go back to 7/29
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
No luck on the logcat either, now that I have the ADB daemon streaming the log to my PC, I can't seem to make it crash or lock up. Although, I wasn't on a USB cord every time it died, and now I am, so maybe that's related? I know the device can't deep-sleep when plugged in...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Has anybody tried the kernel from build 2 and flashed it on build 3? I think the reboots are from the new cpufreq changes. If we could get some feedback cm could get it fixed faster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aimfire72:
I take it back... After running stable for several hours:

- email notifications not working

- screen went black during middle of important call, battery pull was only way to reboot

Back to stock. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
Have you downloaded the build with a "3" in the middle of the name? If so did you wipe data/factory reset, system, data (yes, in mounts and storage too), cache, and dalvik cache then flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drksilenc:
all 3 builds are having issues atm therom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
With Build 3, I did have one random reboot, happened when I re-enabled Bluetooth after leaving a customer's house.

I will say, I don't get reboots/black screens as much as others (had a big issue on the way to the customer's house, but I found out it's the Songza app, not the CM10) because my phone is usually always plugged in. With how much streaming I tend to do, I can kill a battery in under 5 hours without batting an eye.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
I'm actually not having any problems with the rebooting things.

I am however annoyed by the periodic millisecond white flashes that happen through my whole screen. It particularly happens when I'm typing, like right now, I went through 6 flashes while doing this.

Anyone else have this problem as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Xandlinger:
I am having no problems with build 3, did a dirty install over build 2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Yep - Same thing here.

Thankful I'm only getting this and not the greenscreen//freeze/reboot like a lot of the others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kurant1:
I have build 3. I've flashed even over the top and of the 7/29 build trying to get it to work. No dice. Same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastergrillo:
I was having the reboot problem but did a clean install and now I'm not having any problems like the ones stated. Finally gonna keep this as a daily driver thx cyanogen great work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Nevermind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I'm on 3, had no reboots, calls have been ok. Did do a full wipe, no delvik clear though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
The reason it is not a Daily Driver is simply the audio bug... I personally need my phone to ring... I use it for business and cant miss calls or texts... But I agree once the audio bug is fixed it will be a great AOSP rom till it gets truly CMed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cirusnb:
Totally agree with all points, My dl speed with this ROM went from 12mbits to max 5 mbit also, not sure if its related, funny you mention the ROMmanager backup, I just did it to go back to AOKP. . but it looks very promising, i did a CF bench on it, for fun (old but just figured I'd try it) only scored 5000. so I do agree its very very very early to use this for a Daily rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] weedolo9y:
First things first are you really asking this question when it clearly stud you are in the s3 forum? ! So obviously its for the s3 if it was for the s2 it would probably be in the s2 forum. .. just saying common sense

Sent from my SAMSUNG-SGH-I747 using Xparent ICS Blue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yokken:
exFAT is proprietary and only the Samsung kernels have support for it. Otherwise, you must format your card to FAT32. There's a guide in the forums.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
It will show up as H in HSPA and 4G in LTE.

I agree with others. If you don't need audio, its easily a daily driver. I personally don't. My phone is usually right in my face so if I get a call I can see it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Maybe I missed it - updated post to reflect H for HSPA+
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I can confirm that ad2p is not working correctly. My media center in the car can have my phone play/pause, but the audio only goes through the phone. Can others confirm this as well.

---------- Post added at 12:30 PM ---------- Previous post was at 12:30 PM ----------

Also its rw-r--r-- you had e in there :D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
got it thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] groggrog:
With ROM Manager Premium v5.0.0.8, should I be seeing the Galaxy S3 in the list of devices? I'm not, so am wondering if anybody can tell me how to get it in there so I can install this ROM. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrakifa:
ROM manager showed me the att galaxy s iii option...not sure why its not showing you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Shows up fine on mine it should say AT&T Galaxy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] groggrog:
Very strange, definitely not showing up in mine. I see Samsung Galaxy Note (AT&T), Samsung Skyrocket, and Samsung T-Mobile GalaxyS2, plus about 20 non-Samsung devices. I even uninstalled ROM Manager and reinstalled it. Are there any dependencies for it that I may not have installed?

Thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
try uninstalling, then reboot, and re install - also I am running premium so that might be a bit different... I believe to use it for CM9 and CM10 updated you need the paid version... I could be wrong but int he rom section for cm9 it says premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] groggrog:
I am running Premium. Haven't rebooted since purchasing though, so will try that. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yaotl:
Not using Premium here and it shows up in cm9. There are a bunch of incorrect phones listed, but it's in there.

wait, are we talking about the rom or cwm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
mine wasn't showing it either with the latest rom manager downloaded from market. i just installed the new recovery through terminal emulator.

I pretty much followed the instructions here. http://www.theandroidsoul.com/easy-guide-install-clockworkmod-recovery-verizon-galaxy-s3/ and made changes where necessary.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
Thanks for sharing. Unfortunately, LTE still doesn't work using the stock APN settings you posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
AT&T galaxy s3 shows up in Rom Manager basic but you can not updated CM9 via rom manager unless you have premium... refer to image a couple post up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] groggrog:
Still not seeing the Galaxy S3 in the ROM Toolbox, but was able to install CM10 from recovery mode...thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
The original post said you had to flash the camera fix file and the new GAPPS for JB - the link posted here is for the JB Gapps - the link for the Camera Fix is on the previous page - go back one or two pages and you will see really long post that talks about why this isn't that persons daily driver - the link to the camera fix is in the middle of the post.

Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I think he gets the point that there is a rebooting problem and a inversion problem. I don't think we really need 20 or so pages with the same redundancy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
I dont believe discouraging people reporting bugs is what is needed here. We really dont know what is causing these random reboots and by stifling the conversation, we (as a group) will never be able to help the OP solve this issue.

If the mods want change in this thread, Im sure they will/can inact that change.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I think it should be new bugs not 20 pages of the same problem over and over and over again......

It has already been stated that people did a full wipe and the issue is there.

You should not have to dirty flash anything if you do then there something wrong. Posting the same things over and over again only makes it harder to find the post about new bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
Justin... Love your gapps bro...

But all these little tidbits of info might help the OP. I dont see the same EXACT bugs being reported. People are trying and doing things all kinds of ways.

I wish i could put my finger on it or knew more to help, but again, I disagree with "lets move on". I say keep posting till we get it figured out.

But its just my humble opinion :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
None it matters without a log cat. Can't debug a comment in a thread... :rolleyes: just sayin
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Possibly because you're charging... mine seems to be deep sleeping less than previous, tho
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I'm saying we have 30 post saying "I had reboots" and only a handful of logcats. I made no comment towards you and your post. You should care btw, there is a zero tolerance for bad attitudes and that kind of comments does not help development.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Can't get a logcat when a random reboot happens either. As far as I know, a reboot would clear out any logs for such. Now if there is a persistent crash log that we can pull, I'll be glad to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewdatrip:
More logcats less bickering thanks

Keep it clean folks.

Cyanogen is working his tail off here

Thanks to everyone providing issues with logcats

Drew
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
You could always go into recovery after the reboot and pull logs.

My cheat sheet when I'm working with a dev debugging...

How To Find Wakelocks:

adb shell cat /proc/wakelocks > wakelocks.txt

How To Get dmesg logs:

adb shell dmesg > dmesg.txt

How To Get Logcat:

adb logcat -d > logcat.txt

How To Get kmsg:

adb shell cat /proc/last_kmsg > kmsg.txt

Found an extra one that I have not tested that should be activated before reboots to capture it.

adb logcat -v time > logcat.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
I'll see what I can do next time, the only random reboot I've had happened when I was nowhere near a computer. Doesn't make it easy to capture a log through recovery. Are you saying when a random reboot happens, pull the battery, then go into recovery? My question is, at what point during a reboot are the logs cleared? If it's the moment you see the Cyanogenmod logo, I have a very narrow window considering I'd have to take off my case to yank the battery, and holding the power button is a 10 second affair. I'm not trying to be difficult, I'm asking a genuine question, if so I'll switch to an easier to remove case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Honestly I am not sure when and if the logs are purged. The only way I can reproduce a reboot for me is while on call I keep pulling the phone away from my face and back to make the sensor turn the screen on/off. I wouldn't think we would have to go as far as pulling the battery but I am not sure about the window. I know the dmesg is for kernel after a crash/reboot and the kmesg is for the kernel while it is active (or viceversa, I just pull logs to help the developer and when I do pull them, they are able to resolve the issue quickly). I understand crashes happen and people want to report them, but it helps the community if we can follow up the post with logs to help isolate the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Open your terminal on your phone...

su

logcat > /sdcard/log.txt

Then.. make your call... 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 :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Is that still updating the logcat after initializing? I thought that command only created the logcat for the moment and it ends. Thats why I was looking for the command that has the logcat to continue while reproducing the bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
so.. if anyone has had any issues with the phone going to sleep and not waking up (key lights on, but nobody home) It seems to happen around whenever i change Bluetooth, and i think also when i mess with wifi..

but thats just a guess. hope that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
It continues if you type it the way I put. You will notice it doesn't return a prompt after you type it, it continues to write to the file
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aquethys:
Just a curious question. The log cat command you specified...does it write the things that happened starting at boot too or just the things after the command is entered?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
It will dump everything since last boot and then start writing to the end
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
If you're trying to catch a reboot and the boot-up process just afterwards as well, it would have to be hooked up using adb, but it may not reboot since it's hooked up...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
Got a reboot I'm @ work put got "safe mode"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peaster3:
After six hours of use, I don't seem to be having any issues. If it will help anyone, my process was this:

Nandroid (I used my nan of the 7/29 release)

Moved Nandroid to external sd (just to be safe)

Go into recovery

Wipe data x3 (only once is necessary, but playing it safe)

Wipe cache x3

Wipe Dalvik x3

Flash rom

Flash gapps

Go to backup and restore

Advanced restore (my Nandroid was still there)

Restore data

Reboot and bake for a few minutes

All apps and data intact and no issues so far.

I'm not a dev (yet), but I just want to contribute any way I can. Outside of the bashing, this community is great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naria01:
F8? :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] irish.iolar:
8/8 running for a day now, 1 forced reboot after trying to make a picture my wallpaper but since that, everything's perffect, Soo smooth. Awesome work man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonziter:
Using 08/08-3. Did full wipe x3, cache x3, dalvik x3. Installed the ROM then gapps 07/26 immediately after flashing the rom. Then just allowed it (gapps) to restore files over WiFi. No problems today AT ALL. No kernel changes. I did not use any 3rd party app to restore apps installed on another ROM. Yeah it takes more time, sure, but I never have issues if I flash like this.

This thing works very nice. Super impressive. Bluetooth / A2DP works beautifully. Sorry to brag, but no complaints. One big bucket of Land-o-Lakes for me here!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewdatrip:
Removed.

Sorry wrong thread

Drew
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeahmann:
Seeing that some people are having no reboots and some like myself are having lots of reboots, it could be a heat issue brought on by the heavily reworked kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
You want to hear the odd thing about your observation...I have had two reboots so far. Oddly enough both times while on Wifi, and both while in the middle of downloading CM10-08-2 and the other was while downloading CM-10-08-3 earlier today!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
I finally did have a black screen issue. Had to pull the battery. Its only happened once when I was at work and phone was idle for over 2 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
Multiple Wiping

Wiping multiple times is not only unnecessary, but this is a *flash* device, and there are a limited number of writes to each sector. Wiping over and over adds unneeded wear to your device, which could cause premature failure. It's not like the format just accidentally doesn't erase everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kyan~:
tried flashing 69rooted stock.tar through odin after using cyanogen 10 build 2..stuck on boot. flashed the sammobile i747.tar.md5 through odin...stuck on boot. anyone can help me here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
Not in front of PC, but I had same issue, a few days ago. I had to flash an older version through pre rooted stock version. I used the one in the thread on how to flash without tripping the flash counter. Sorry for the lack of detail man

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Did you remember to wipe out your data beforehand? You probably will have to boot into Samsung Recovery (Should be the same way as CWM) and wipe out your data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
Does 67 sound right maybe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kyan~:
69 is ucagl1 rooted

---------- Post added at 07:17 AM ---------- Previous post was at 07:16 AM ----------

<3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
It happens, you forgot that ODIN won't wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kyan~:
i remember previously on sgs1 it did right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I'll put my 2¢ in on the reboot/black screen thing:

I came from stock UCLM, wiped data installed 08/08 #2, Right after boot I did get one black screen. Pulled the battery, rebooted, downloaded #3, installed with no wipe. Havent had a single issue since
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
This is the kind of info needed for the OP or the Q&A OP. Good stuff man, we take these things for granted when you've done them for so long.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
I can't speak on the SGS1 since I never owned it.